Session initiation protocol system timeout timer method

ABSTRACT

The present method provides for a session initiation protocol timing arrangement which facilitates instant communications in a packet data communication system ( 50 ). Each network server ( 15 - 25 ) sets a time out timer ( 92 ) which is coordinated with each of the downstream network servers. Network server ( 15 ), for example, sets a time out timer value which is selectable by the system operator. Subsequent network servers ( 20  and  25 ) then set the value of the time out timer to be that of the originating server ( 15 ) or client ( 10 ) less a fixed time such as one second. Further, a provisional message ( 118 ) is sent through the network to avoid expiration of the time out timer in upstream stages.

BACKGROUND OF THE INVENTION

The present invention pertains to packet data communications systems andmore particularly to session initiation protocol time out betweenclients and network servers.

Internet protocol (IP) using session initiation protocol (SIP) enablesmodern communication networks to [provide many packet data servicesincluding voice to wireless users in a dispatch environment. Sessioninitiation protocol provides for certain methodology for timing overallcommunications between clients and servers and servers and other serversin a network to avoid a miscommunication or lack of communication. Suchsituation is called a time out period.

The session initiation protocol standard timer value is initially set atone-half second and is doubled for each successive retry. The overalltransaction time out timer is set for a maximum of 32 seconds and wouldautomatically expire prior to sending the maximum number of retries.

Typically data packets are sent through several “network hops”. A hop isa transmission of the data packet from one node to another. For example,from an originating server to a group or interconnecting server or froman interconnecting server to a terminating server. The number of networkhops depends upon the particular routing of the data packet. As a datapacket is transmitted from network hop to network hop, the time outtimer of the originating server is constantly running and for lack ofresponse by down stream network servers, it may time out. Between thetime of initiation and time out by a network server, several retries mayhave been attempted by the originating server. The downstream networkservers have no knowledge of the time out of the upstream servers. Thisresults in call cancellations and drops and further a race conditionexists between network servers. Some network servers may still beprocessing the packet data while upstream servers are attempting tocancel the packet data transmission since a time out of the upstreamnetwork server has occurred.

Further, for particular kinds of packet data uses such as dispatch andspecifically push-to-talk functions, a time out time period of 30seconds is a long time for the push-to-talk type service.

In a session initiation protocol based packet communication system, thetime out timer is governed by document RFC2543BIS-09. No resolution ofthe above problem or recognition of the problem is expressed for thetime out timers in this document.

Accordingly, it would be highly desirable to have a time out timercoordination method between successive “network hops” or networkservers.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a block diagram of a packet data communication network inaccordance with the present invention.

FIG. 2 is a flow chart of a time out coordination method in accordancewith the present invention.

FIG. 3 is a message flow diagram depicting network server coordinationin accordance with the present invention.

DESCRIPTION OF THE PREFERRED EMBODIMENT OF THE INVENTION

Referring to FIG. 1, a block diagram of a packet data communicationsystem 50 which employs session initiation protocol (SIP) is shown.Communication system 50 is shown and includes an originating client 10which is coupled to an originating server 15 which in turn is coupled toa group server 20. Group server 20 is coupled to terminating server 25.Finally, terminating server 25 is coupled to a terminating client 30.Originating client 10 is attempting to connect and communicate withterminating client 30. One application of communication system 50 may bebetween two clients 10 and 30 communicating in a push-to-talk servicearrangement.

As an example, originating client 10 is attempting to communicate withterminating client 30. A SIP invite request is sent by originatingclient 10 to originating server 15. The message flow for this purpose ofconsideration is from left to right. That is, originating client 10 isupstream with regard to originating server 15; and originating server 15is downstream with respect to originating client 10. Terminating client30 is downstream with respect to each of the blocks of FIG. 1, that is,originating client 10, originating server 15, group server 20 andterminating server 25.

Generally, each server 15-25 provides for timing of messages sent to thenext server downstream. For lack of acknowledgment each client andserver returns an acknowledge message in response to a SIP invitemessage. If messages become delayed or lost a retry of the SIP invitemessage, for example, is attempted. The present invention resets theretry timer for each retry instead of linearly or exponentiallyincreasing it. Further, each time a SIP response message is receivedfrom a downstream unit (response message=1XX), the retry timer is resetand the overall time out timer is set with a period of one secondgreater than the next node (server or client) upstream. As a result anysubsequent provisional SIP responses (1XX) would reset the time outtimer prior to its expiration. Further, this invention calls for the useof a provisional response code (181 forward) to be used for each nodeupstream to be returned to the previous downstream node. This 181forward response code allows the time out timer to be reset and avoidscanceling any retries.

Referring to FIGS. 2 and 3, a flow cart of the time out timer method 60is shown. The method is started and block 62 is entered. Block 62selects a primary contact from an associated database. That is, once aserver receives a SIP invite request 110 from a client or an upstreamserver, the database is consulted to determine the next primary serveror end server which may handle this invite request. The contact iseither the next server downstream or the terminating client depending onthe flow through the communication system 50.

Next, a retry count is set equal to two. This counter keeps the count ofthe number of retries made by a server. The retry count may be setdifferently for different servers depending upon the needs of thenetwork operator and other traffic considerations.

Next, block 66 sends a SIP invite to the contact obtained from thedatabase in block 62. Again, the contact is either the next server orthe terminating client. For example, using FIG. 1, since originatingserver 15 has already obtained the SIP invite from originating client10, the next contact for originating server 15 would be group server 20.Therefore, the SIP invite would be sent from originating server 15 togroup server 20.

Next, the retry timer is set to a value of one-half second, block 68.The retry timer value is also settable based upon the needs of thesystem operator and other traffic conditions. The server then waits fora response from the next server downstream or terminating client. If noresponse is received from the next downstream server, block 70 transferscontrol to block 72 via the no path. Block 72 decrements the retrycounter. Remember originally the retry counter in this example was setto two. Next, block 74 determines whether the retry counter is zero. Ifthe retry counter is zero, three retries of sending the SIP invite tothe next server have been attempted. Block 74 then transfers control toblock 76 via the yes path. Block 76 determines whether an alternatecontact is included in the database. Remember that a contact is a nextserver or terminating client in the downstream flow. For terminatingclient an alternating contact may be a computer instead of a cell phoneor telephone. If there is no alternate contact in the database, block 76transfers control to block 80 via the no path. Block 80 indicates thatthe process has failed and ends the method.

If an alternate contact is included in the database, block 76 transferscontrol to block 78 via the yes path. Block 78 selects the alternatecontact from the database. Then block 78 transfers control to block 64which reestablishes the retry count at two. The method then sends theSIP invite to the alternate contact, block 66, sets the retry timer toone-half second, block 68 and waits.

If the server sending the SIP invite receives a final response, forexample, a SIP 200-699 message, block 70 transfers control to block 82via the final response path. Block 82 sends back the final responsemessage to the previous contact. The final response message is not sentto the originating client if that was the contact. The retry timer iscanceled, block 84. The process is indicated as completed successfully,block 86. Then the process is ended.

If the server sending the SIP invite detected a provisional response,block 70 transfers control to block 88 via the provisional responsepath. Block 88 sends back the provisional response indication to theupstream server. Next, the retry timer is canceled, block 90. Then block92 sets the timeout timer value equal to 13 seconds. The value of thetimeout timer is settable by the system operator depending upon thesystem operator's needs and other traffic conditions. Each downstreamserver sets the time out timer to approximately one second less than theupstream server or originating client. This prevents the cascading ofSIP cancel messages.

Next, block 94 waits for a response. If a provisional response isreceived, block 94 transfers control to block 96 via the provisionalresponse path. A provisional response is a SIP message between 100 and199. Block 96 cancels the time out timer. Next, block 98 sends back(upstream) the provisional response, unless the upstream network nodewas the originator. Then block 98 transfers control to block 92 to setthe time out timer and wait.

If the received response is a time out, block 94 transfers control toblock 106 via the time out path. Block 106 sends a SIP cancel messageback upstream, unless the previous upstream node was the originatingclient. Then the process is indicated as having failed, block 108 andthe method is ended.

If a final response was received, block 94 transfers control to block100 via the final response path. Block 100 sends the final responsemessage back to the upstream server, unless the upstream unit is theoriginating client. Next, the time out timer is canceled, block 102. Theprocess is then indicated as being completed successfully, block 104.The method is then ended.

FIG. 4 depicts a message flow diagram which diagrammatically depicts asample message flow for the method of FIGS. 2 and 3. Originating client10 sends a SIP invite message 110 to originating server 15. The retrytimer is initialized to one-half second (not shown). Originating server15 may return a SIP 100 trying message 112 to originating client 10.Originating server 15 also forwards the SIP invite message 114 to groupserver 20. Two retries of the SIP invite message are shown beingtransmitted from originating server 1 to group server 20.

Group server 20 finally responds to one of the SIP invites with a 100trying message to upstream originating server 15. This 100 tryingmessage is not returned to the originating client 10.

Group server 20 then sends the SIP invite 116 to terminating server 25.Subsequently, two retries are made to again send the SIP invite toterminating server 25. The SIP invite message is then alternately routedto a terminating server 26 and when the SIP invite message is resent aSIP 100 trying message 117 is returned from terminating server 26 togroup server 20.

Further, prior to sending the 100 trying message 117, group server 20sent a 181 forward message to originating server 15 indicating that thecall was being routed to an alternate terminating server. Originatingserver 15 sent the 181 forward message to originating client 10. Thisenabled originating client 10 to reset the time out timer prior to itsexpiration. In addition, the time out timer for originating server 15 isset to the value of the time out timer (TT) less one second.Additionally, the time out timer of group server 20 is set to the timeout time period of originating client 10, TT−2 seconds since it is twohops downstream with respect to originating client 10.

Alternate terminating server 26 then attempts to forward the SIP invite121 to the terminating client 30. Again, two successive retries are madeunsuccessfully. The method of FIG. 2 then selects an alternate contactor in this case terminating client from the database. This correspondsto perhaps a cell phone when the terminating client was unable to bereached at the computer.

The alternate terminating client 31 is then selected.

Meanwhile, the terminating server 25 sends a 181 forward message 122 tothe group server 20. This message is then cascaded in messages 124 and126 back to the originating client 10. As a result the time out timer isreset prior to expiration.

When the alternate terminating client 31 is rung on the cell phone, theresultant message 180 ring 128 is sent to terminating server 25 andcascaded back through the upstream network as 180 ring message 130 tooriginating client 10.

Lastly, the terminating server 25, in this example, was unable tocomplete the coupling to the alternate client 31 and as a result, timeout timer 131 expired. The value of time out timer was the originalvalue of timer set by originating client 10 minus three seconds sincethere were three hops between the originating server and the terminatingserver. As a result, terminating server 25 sends a cancel message 132 tothe alternate terminating client 31. Further, a 408 time out message 134is sent upstream through the network back to the originating client 10.This indicates the call was not complete because of time out.

As can be seen from the above explanation, the present method preventspremature time out and cascading of time outs throughout thecommunication system. The total response time by the system is not afixed number but is a function of the number of “hops” made through thesystem and the number of alternate elements in the system. This methodallows for a variable number of provisional attempts or retries.Further, this method resets upstream timers by the sending of aprovisional 181 forward message to stop time out timers. This methodeliminates race conditions among the various servers of thecommunication system. Further, this method provides for service operatorselection of several parameters.

Although the preferred embodiment of the invention has been illustrated,and that form described in detail, it will be readily apparent to thoseskilled in the art that various modifications may be made thereinwithout departing from the spirit of the present invention or from thescope of the appended claims.

1. In a Session Initiation Protocol (SI) based communication system, atimeout timer method for SIP messages transmitted among clients andservers, the timeout timer method comprising the steps of: sending a SIPmessage from a client to a server or from a first server to a secondserver; setting by the client or the first server a first value of afirst timeout timer; setting by the first server or the second server asecond value of a second timeout timer, the second value of a secondtimeout timer being less than the first value of the first timeouttimer; and forwarding the SIP message by the first server to the secondserver.
 2. In a SIP based communication system, the timeout timer methodas claimed in claim 1, wherein there is further included a step ofreceiving a provisional message by the first server or the secondserver, said provisional message indicating an alternate activity by theSIP based communication system.
 3. In a SIP based communication system,the timeout timer method as claimed in claim 2, wherein responsive tothe provisional message, the first server or second server cancels itstimeout timer.
 4. In a SIP based communication system, the timeout timermethod as claimed in claim 3, wherein there is further included a stepof sending the provisional message by the second server or first serverto the first server or to the client.
 5. In a SIP based communicationsystem, the timeout timer method as claimed in claim 1, wherein there isfurther included a step of receiving a final response message by thesecond server or the first server, said final response messagecorresponding to a successful operation by the SIP based communicationsystem.
 6. In a SIP based communication system, the timeout timer methodas claimed in claim 5, wherein there is further included a step ofsending the final response message by the second server or the firstserver to the first server or to the client.
 7. In a SIP basedcommunication system, the timeout timer method as claimed in claim 6,wherein there is further included a step of canceling by the secondserver or the first server its timeout timer responsive to the finalresponse message.
 8. In a SIP based communication system, the timeouttimer method as claimed in claim 1, wherein there are further includedsteps of: receiving by the second server or the first server a timeoutresponse; and responsive to the timeout response, sending by the secondserver or the first server a cancel message to the first server or tothe client.
 9. In a SIP based communication system, the timeout timermethod as claimed in claim 1, wherein the step of sending the SIPmessage includes a step of sending a SIP invite message.
 10. In a SIPbased communication system, the timeout timer method as claimed in claim1, wherein there are further included steps of: selecting by a client, afirst server or a second server a retry count value; and selecting bythe client, the first server or the second server a retry timer value.11. In a SIP based communication system, the timeout timer method asclaimed in claim 10, wherein there is further included a step ofmaintaining the initial value of the retry timer value for subsequentretries.
 12. In a SIP based communication system, a timeout timer methodas claimed in claim 10, wherein in response to expiration of the retrytimer there are further included steps of: decrementing the retry countvalue by one; determining whether the retry count value is equal tozero; and if the retry count value is not equal to zero, iterating thestep of sending the SIP message.
 13. In a SIP based communicationsystem, the timeout timer method as claimed in claim 12, wherein if theretry count value is equal to zero, there is further included a step ofdetermining whether an alternate contact for the SIP message exists. 14.In a SIP based communication system, the timeout timer method as claimedin claim 13, wherein if an alternate contact exists, there are furtherincluded steps of: selecting the alternate contact from a database; anditerating the steps of claims 10-14.
 15. In a Session InitiationProtocol (SIP) based communication system, a timeout timer method amongnetwork nodes, the timeout timer method comprising the steps of: sendinga SIP message from a first network node to a second network node;setting by the first network node a first value of a first timeouttimer; and setting by the second network node a second value of a secondtimeout timer, the second value being less than the first value.
 16. Ina SIP based communication system, a timeout timer method as claimed inclaim 15, wherein there is further included a step of sending aprovisional message from the second network node to the first networknode, the provisional message indicating that the SIP basedcommunication system is processing alternate routing.
 17. In a SIP basedcommunication system, a timeout timer method as claimed in claim 16,wherein responsive to the provisional message there is further includeda step of stopping the second timeout timer.
 18. In a SIP basedcommunication system, a timeout timer method as claimed in claim 17,wherein there is further included steps of: sending by the first networknode the provisional message to a previous network node; and stopping bythe first network node the first timeout timer.
 19. In a SIP basedcommunication system, a timeout timer method as claimed in claim 15,wherein the SIP based communication system includes a dispatchcommunication system supporting push-to-talk services.
 20. In a SIPbased communication system, a timeout timer method as claimed in claim15, wherein the SIP based communication system includes an iDENcommunication system.